You are not required to migrate your e-Content Manager (e-CM) 5.x content into the WCM environment. Your e-CM websites can coexist alongside newer WCM websites and share the iMIS database without collision.
Note: The e-CM content being migrated must exist in your current production iMIS database; it cannot be migrated from a different database.
Caution! Back up your production iMIS database before performing this procedure, so that you can restore your previous e-CM environment if the migration results are not satisfactory.
To prepare your e-CM content for migration
■ Because e-CM allows duplicate tag names but the WCM environment does not, you should review your existing e-CM tag hierarchy to ensure that all tag names are unique and that all tag references in your content are correspondingly revised. The migration will succeed even if you don't clean up your duplicate tags, but the migration utility will consolidate all the duplicates into one tag, which might have undesirable results.
■ If you have any websites with the same name in your e-CM environment, you should rename them to have unique names. If the migration utility encounters multiple websites with the same name, it will automatically rename all but one of them by appending a number to the end of the website name.
Aside from these two preparatory steps, your best planning tool is to perform one or more test migrations as described in the following section, then examine the test migration results to determine what else you can adjust beforehand to achieve the best results.
To perform a test migration without affecting your production content
The migration utility can be used to perform a test migration from your production iMIS application server and database to a test application server and database, which can enable you to safely determine how much effort it will take to successfully migrate e-CM in your production environment.
■ Your e-CM 5.x content must be stored in your production iMIS database.
■ You must ensure that the test iMIS database used by your test application server is a very recent copy of your production iMIS database. What's important is that all the iMIS user records are identical in each database. If there are any differences in the user records, the migration from one database to another will fail.
■ Perform the same procedure as in To migrate e-CM 5.x content below, but specify your production iMIS database as the source database and the test iMIS database as the destination database.
■ Perform the recommended post-migration tasks and examine the resulting WCM websites on the test application server to help you determine additional pre-migration tasks and post-migration tasks that will give the best results.
■ Reset your test iMIS database back to its pre-migrated state if you need to run the test migration again. Once you are satisfied with the migration results, perform the To migrate e-CM 5.x content procedure on your production iMIS database and then perform your planned post-migration steps.
To migrate e-CM 5.x content
If you prefer to migrate your websites from a ColdFusion environment to an ASP.NET environment for ease of extension and integration with iMIS, you must first plan your pre- and post-migration tasks by reviewing the Differences between e-CM 5.x and WCM section. Then you use a command line utility to migrate existing e-CM content into the WCM environment. After migration, you perform your planned post-migration cleanup steps.
You should then be able to publish the migrated content and use the Surf-to-Edit feature of WCM to discover and fix any remaining issues that you might not have anticipated.
Once the migrated content has been cleaned up in this manner, you can begin working on any ASP.NET customizations that you might have planned to provide the same functionality in WCM that you had previously created using ColdFusion in the e-CM environment.
The specific steps that you must follow to migrate the e-CM content are as follows:
1. On the SQL Server host that contains the destination iMIS database into which you are migrating the e-CM content, execute the following script with appropriate modifications to specify the connection parameters to your iMIS database (which contains the e-CM content). The values that you should change are delimited with brackets [ ] (do not include the brackets in the script).
DATE SystemConfig
SET ParameterValue = 'CM5:Data Source=[hostName];
User ID=sa;
Password=[saPassword];
Initial Catalog=[catalogName];'
WHERE ParameterName = 'SecondaryConnection'
AND ParameterValue LIKE 'CM5%'
2. On your production iMIS application server, use a text editor to open CM5MigrationTool.exe.config (located by default in C:\Program Files\ASI\iMIS15\Net\bin\) and perform the following actions.
□ In the <connectionStrings> declaration, verify that the connectionString attribute specifies the correct connection parameters for your iMIS database. The values that you should change are delimited with brackets [ ] in the following example (do not include the brackets in your edits)
<connectionStrings>
<!-- datasource for the destination database.-->
<add name="DataSource.iMIS.Connection";
connectionString="server=[hostName];
database=[dbName];
uid=sa;
pwd=[saPassword];" />
</connectionStrings>
□ In the <SystemParams> declaration, modify the value attribute of the SourceRootLocation key to specify the physical path where content source files (the e-CM equivalent of uploaded files associated with ContentFile iParts) are stored on the IIS server where your e-CM websites are hosted. This value is specified in SourcePath parameter of the Configuration Settings for your e-CM environment. Here is an example of that section:
<add key="SourceRootLocation" value="C:\Inetpub\Source" />
□ Save your changes.
3. If the e-CM server is not also your production iMIS application server, copy the following files to a temporary folder anywhere in the file system of your e-CM server. The default location for these files on your production iMIS application server is C:\Program Files\Asi\iMIS15\Net\bin.
□ CM5MigrationTool.exe
□ CM5MigrationTool.exe.config
□ Asi.Business.ContentManagement.dll
□ Asi.dll
□ Asi.Lexicon.dll
□ Asi.Membership.dll
□ Asi.Web.dll
4. On the e-CM server, open a Command Prompt window and navigate to the folder that contains CM5MigrationTool.exe.
5. Type CM5MigrationTool.exe, then press Enter to run the utility. When the prompt reappears, the migration has finished.
To clean up your migrated content
There might be additional post-migration steps that you must perform, based on the results of your test migrations, but at a minimum you must perform the following tasks to clean up your migrated content.
1. Examine your migrated WCM website definition and make the following fixes.
□ In the Properties section, verify that the migrated website's URL(s) pointing to the IIS website root correctly match the physical path of the IIS applications or IIS web sites that host the migrated WCM website.
□ In the Site Look and Feel section, apply your theme elements.
2. Examine your migrated website's sitemap and make the following fixes.
□ Specify one of the navigation items in the sitemap to be the default page for the website, because the migration utility sets the default page to Default.aspx, which is probably not what you want.
□ Fix broken URLs in your navigation items. The link path that you see in the migrated navigation item can provide clues where the original content was located in the e-CM environment.
3. Examine your migrated content records and make the following fixes.
□ Fix broken URLs in your ContentFile, ContentLink, and ContentReference iParts in your migrated content records. Also check your ContentHTML iParts for any hard-coded links that might need to be fixed.The link path that you see in the migrated content records can provide clues where the original content was located in the e-CM environment.
□ Because WCM features true tag inheritance, your converted ContentTaggedList iParts will now include content records that are tagged with any descendant of a tag that was specified in the original e-CM tagged page. You might therefore want to review the rendered output of the ContentTaggedList iParts and rearrange the tag hierarchy to achieve the results that you desire.
□ You must manually reapply display masks to all tagged list formats.
□ If your e-CM website name comprises multiple words separated by spaces, you will end up with two migrated content folders related to the migrated website: one with the original name of the website and another with an underscore character between each word. For example, ASI USA and ASI_USA. The one with underscore characters contains all the content records that were created from e-CM navigation items that had content in them. It can make ongoing web content authoring easier if you move the content records from the folder with underscore characters into the other folder, then delete the empty folder.
4. Copy all images from your e-CM environment (typically sourced in the AM/Images folder) into the WCM environment using Manage Images in the Content Designer tool. (See Managing images for use in content records for more information.) For the converted content records to find these images, they must have the same relative URL as they had in the e-CM environment. This means you must either:
□ Place the images into the exact same folder below the root of the physical path for the IIS applications and IIS web sites that host your WCM websites.
□ Or if you cannot achieve the same relative URL in the WCM environment, you must change your migrated content records to point to the new location for the imported images.
5. If you used HierMenu to implement pop-up menus in the e-CM environment, you must reimplement these using ASP.NET techniques in your master pages.
To remove the migrated content and re-migrate it from e-CM 5.x
The migration process includes websites and content records. If you have previously migrated e-CM 5.x content and you wish to perform the migration again (for example to re-migrate some content or websites you have modified in e-CM 5.x since the original migration), you must purge the migrated websites and content records. Otherwise, the migration tool will generate an error.
1. Recycle and purge the migrated website(s).
□ From Content Management, select Site Designer > Manage websites.
□ Select the website(s) you wish to delete, then from the toolbar select Organize > Delete.
□ Select the Recycle Bin, and from the toolbar select Organize > Empty the Recycle Bin.
2. Recycle and purge the migrated content
□ From Content Management, select Content Designer > Manage content.
□ Select the content folder(s) you wish to delete, then from the toolbar select Organize > Delete.
□ Select the Recycle Bin, and from the toolbar select Organize > Empty the Recycle Bin.
Caution! Do not delete the @/iMIS content folder or any of its contents as this folder contains content required for iMIS itself to function. To restore previously migrated content, see To preserve migrated websites or content below
3. Execute the following SQL in the iMIS database:
□ delete from ContentWorkflowParameters where not exists (select 1 from DocumentMain where DocumentMain.DocumentVersionKey = ContentWorkflowParameters.DocumentVersionKey)
□ delete from CM5Migration where ImportItemType in ('Website', 'WebsiteContentFolder', 'ContentFolder', 'ContentAreasFolder', 'Content', 'Nav_Menu')
To preserve migrated websites or content
Use these instructions if you wish to preserve a modified version of a previously migrated website or content rather than replacing it with a re-migrated version. For example, you migrated e-CM 5.x content into Content Management and then modified it in Content Management, and wish to keep the Content Management-modified version rather than the re-migrated version from e-CM 5.x.
1. Export the content or website you wish to preserve after migration. For more information, see To export and import objects between your staging and production servers in the Importing content from a staging server topic.
2. Perform the steps above under To remove the migrated content and re-migrate it from e-CM 5.x.
3. Run the migration tool.
4. From Content Management, select Content Designer > Manage content.
□ Select the content folder(s) you wish to replace with the exported version, then from the toolbar select Organize > Delete.
□ Select the Recycle Bin, then from the toolbar select Organize > Empty the Recycle Bin.
5. Re-import the exported version.
6. Perform the post migration clean up steps described above on any re-migrated website(s) or content.
Troubleshooting
■ You must have administrative access to Internet Information Services (IIS) and the entire file system on your iMIS application server and on all the external web servers that you use for hosting WCM websites.
■ You must be a member of the iMIS SysAdmin security role.
■ You must review the Differences between e-CM 5.x and WCM section to help you decide if a migration of your e-CM content is right for your organization's website. You must also plan any pre- and post-migration tasks needed to provide similar website functionality in the new WCM environment.
■ You must know the names of the SQL Server host, database, catalog, and the sa password for your iMIS database.
■ You must know the file system path to where your content source files (the e-CM equivalent of uploaded files associated with ContentFile iParts) are stored on the IIS server where your e-CM websites are hosted. This value is specified in SourcePath parameter of the Configuration Settings for your e-CM environment.
Tips
The following information can be helpful when migrating e-CM 5.x content.
What e-CM 5.x content is migrated?
The following e-CM content is converted to its WCM equivalent during migration. Important details about the differences between original e-CM content and its WCM equivalent are described in Differences between e-CM 5.x and WCM.
■ e-Series security groups
■ Content authority groups (CAGs)
■ Content folders
■ Content records
■ File types
■ Sitemaps and navigation items
■ System settings (e-CM configuration)
■ Tags
■ Tagged components
■ Tagged page layouts
■ URL mappings
■ e-CM User defined fields (UDFs)
■ Websites
Monitoring progress and viewing migration logs
You can monitor migration progress by using your SQL Server management tools to inspect the contents of the CM5Migration table in the destination iMIS database as it is being populated by the utility.
A Log column in this table details all duplicate tags (two or more tags with the same name) from the e-CM environment that were consolidated into a single tag in the WCM environment. (WCM requires that all tag names must be unique.)